Thanks for this PR, @EvgenyOrekhov.
I've tested this in IE8 and other browsers we support and it works perfectly. We should reset display: table on html for mobile browsers too, I think. Everything else looks pretty perfect to me.
You could add a note about this in CHANGELOG.md.

@drublic done

@drublic, did I mess something up? Sorry, I'm new to Git and GitHub.

did I mess something up? Sorry, I'm new to Git and GitHub.

@EvgenyOrekhov don't worry, if it's going to be merge, we'll handle it!

IMHO it looks better when the second line isn't so long (maybe add something like p{ ...; margin: auto; width: 280px; }?).

Note(s):

• Don't know how useful this change is since the 404 is intended to be a placeholder page that users should replace with their own.
• It will not "work" with IE6/7 since they don't support CSS Table displays (reason why display: table wasn't used in the first place + the original idea was to also support them) => v4 shouldn't get this

@alrra I set width to 310px to make sure the word "view" stays on the first line in mobile browsers.

I liked the new 404 page, so I kept using it as it is in my projects, but I kept struggling with proper vertical alignment when I localized the page, so I suggested some h5bp users would also benefit from this change.

P. S. Am I doing it right? I should commit, then git pull upstream master, then git push origin <topic-branch-name>, right? Not git pull --rebase?

Don't know how useful this change is since the 404 is intended to be a placeholder page that users should replace with their own.

@alrra I do think some of the users never touch the 404 page layout. Some just change/translate the text. For those users it will be better if we use this technique for vertical centering. With the technique we use right now the vertical alignment will break for them.

I set width to 310px to make sure the word "view" stays on the first line in mobile browsers.

@EvgenyOrekhov thanks, will check as soon as I get home.

P. S. Am I doing it right? I should commit, then git pull upstream master, then git push origin , right? Not git pull --rebase?

@EvgenyOrekhov After you make your changes and staged them, you can just amend the commit (git commit --amend), and then just force push on your topic branch, in this case to 404-centrify (git push -f origin 404-centrify)

I highly recommend: Pro Git.

I liked the new 404 page, so I kept using it as it is in my projects, but I kept struggling with proper vertical alignment when I localized the page, so I suggested some h5bp users would also benefit from this change.

I do think some of the users never touch the 404 page layout. Some just change/translate the text. For those users it will be better if we use this technique for vertical centering. With the technique we use right now the vertical alignment will break for them.

@EvgenyOrekhov, @arthurvr good to know that people are actually building upon it!

@alrra thanks, I thought "do not rewrite public history" is a strict rule.

I thought "do not rewrite public history" is a strict rule.

@EvgenyOrekhov yes, when it comes to the master branch

@EvgenyOrekhov played a little bit and ended by with this.

• How it looks (some examples):

  Device/OS (Browser)	Screenshot
  Mac / OS X (Firefox)
  PC / Windows XP (IE 6/7) (looks pretty decent)
  iPad / iOS (Safari)
  Samsung Galaxy S III / Android (Chrome)

• The different in size compared to the old 404 is negligible

  • old 404:

    original size:         1242 B
    gzipped size:           574 B
    

  • new 404:

    original size:         1274 B
    gzipped size:           570 B
    

Looking good!

@alrra nice, but it would be even nicer if the line break appeared right after "view", so it could be like

Sorry, but the page you were trying to view
does not exist.

Don't you think?

Note: I've improved the page a little bit more (my previous comment has been updated).

would be even nicer if the line break appeared right after "view"

@EvgenyOrekhov personally I find it nicer the way it is now. :)

@alrra, applied your changes.

Merged in c3a72ff.

Thanks @EvgenyOrekhov and congrats on your first HTML5 Boilerplate contribution! 🎉 👏

Thanks everyone! You made a great first impression of GitHub community!